home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
BBS Toolkit
/
BBS Toolkit.iso
/
wildcat
/
hscat3s.zip
/
HSCATS.DOC
< prev
next >
Wrap
Text File
|
1992-04-12
|
10KB
|
223 lines
H S C A T S
Version 3.0
WILDCAT 3.xx AND HSLINK INTERFACE HELP DOC'S
--------------------------------------------
If you have used HsLink, you know it is a powerful file transfer
protocol that allows you to download and upload at the same time
when the user selects to download with HsLink, essentially
doubling your throughput. HsCats will interface HsLink to Wildcat
so your users can enjoy this terrific protocol on your Wildcat system.
HsCats has three parts PREHSCUP, PREHSCDN, and AFTHSCDN.
These are called from the batch protocol file either HSLUP.BAT or
HSLDN.BAT. Here how it works...pay close attention!
USER DOWNLOAD SESSION:
The user marks off what files they wish to download via Wildcat's file
marking system. Just as they would with any other protocol. They then
select to download and are offered the protocol menu screen. They select
[H] for HsLink and away we go.....
The HSCDN.BAT batch file first calls PREHSCDN.EXE which prompts the
user for an area to upload to (that they have security for) and writes
two files...HSCAT.### (Area chosen by user) and HSACESS.### (which is
the pointer file for areas that they have security to download from).
It will write this info to the HsLink.Cfg file that you point to on
the command line.
AFTHSCDN.EXE will then be called in the batch file and read the
DSZ.LOG and HSCAT.### files and add whatever files where uploaded
during the download session to the Wildcat database. It then updates the
user record for files uploaded and extra time alloted. Wildcat will take
care of updating the user and file database for files that where
downloaded.
************************************************************************
*Special Note*
At present the internal code in Wildcat prevents me from updating the
user's upload or download count and kilobytes. This is something for
which I am not responsible, nor can I change. Wildcat version 3.50 will
have this problem corrected at which time my utilities will be able to
update the user record properly.
************************************************************************
USER UPLOAD SESSION:
The user selects the area to upload to via Wildcat as normal. Then WC
will ask for filenames, descriptions, passwords, keywords, and additional
info as it does for any protocol used. The user then selects [H] HsLink
from the protocol menu as transfer type to use.
The HSLUP.BAT batch file first calls PREHSCUP.BAT which sets up the
HsLink.Cfg file for the proper path to the node's ep directory.
HsLink will then run and send whatever files the user has configured
in the upload transfer to the node's ep directory. At present HsLink
only allows bidirectional transfers to occur when the user selects
downloading. If they select uploading it will only allow the upload
to occur. Hope Sam Smith will add that feature in a future version..
I have the code to make it work in HsCats should he do so.
In a nut shell...it's kinda like merging HsCats and Wildcat together into
one package...simply called HsCats.
SETUP
Setting things up is simple, and we'll go through it step by step.
USE A WORK DIRECTORY FOR YOUR UNARCHIVING OF FILES
Create a new directory to work in. This keeps things much easier to
follow along with and clean up after.
Ok, here we go.
1. Take all the .EXE files from the HsLink archive (HSLxxx.ZIP)
and put them in any directory that you have your dos environment
'path' set up for. Type 'set' at the dos prompt to check. I set
everything into a directory called c:\wc\ep and include it in the
path statement in my autoexec.bat.
2. Do the same thing with the *.EXE files from this (HSCATSxxx.ZIP)
archive. All the files should now be available in the path.
3. Place the copy of HSLINK.CFG I have included into each of your
node home directories. IE: c:\wc30\wcwork\node1, c:\wc30\wcwork\node2,
etc.
4. In each directory that you put a copy of HSLINK.CFG, run
HSCONFIG to make changes necessary for your system. The copy I have
included is a regular setup and should not require much modification.
Make changes to this section as follows. Remember to run HSCONFIG from
the node directory! You should refer to the HsLink Docs for further
information regarding HsLink's options.
A. 'Directory for downloaded files' should be set to your node's
ep directory. HSCATS will do all that work for you for each caller
engaged in a HsLink session. We only need to fill it in the first
time.
5. Complete above step for each one of your nodes if you
are multi-node Wildcat.
7. Copy the enclosed HSLDN.BAT and HSLUP.BAT batch files to your
home directory. Then change to the home directory. Edit whatever you
need to on the batch files I have included for operation on your
system.
8. Run Makewild (still in the home directory) and go to the External
Protocol section. Add HsLink to the external protocol menu as such:
[H] HsLink HSLUP.BAT HSLDN.BAT Y
* Environment Variables, there are a few you need to set to have
HsCats operate properly. Make sure you set the following variables
in each of your cat#.bat files.
IE: Set WCNODEID=(node you are on ie: 1)
Set WCPORTID=(port you are using on that node ie: 1)
Set HOMEPATH=(path to home directory ie: C:\WC30\)
Set NODEPATH=(path to node directory ie: C:\WC30\WCWORK\NODE1\)
* Remember to add the extra backslash at end of directories above.
*************************************************************************
* I now look for 2 more environment variables for the comm routine. *
* They are WCIRQID and WCBASEID respectively. If they are not set in *
* your cat.bat file that starts the node then I default to the settings *
* in your MakeWild.Dat. *
*************************************************************************
* HsCats offers file virus scanning via ScanFile.Bat If HsCats
finds the file "SCANFILE.BAT" it will shell to EMS or DISK before
adding the file to Wildcat's database. ScanFile.Bat will do it's normal
job of scanning the file. If the file fails, HsCats will add it to
the database with the failed scan flag set to Y. It will also subtract
the file and upload kilobytes from the users record.
Again...as stated above in special note, the code will not work on the
user's record at present until Wildcat 3.50 is released this part of
utility will be useless.
At present I have only tested CatScan, which operates properly. Other
scanners may be used but I can only atest to the fact that CatScan causes
no problems. If you are going to use another utility in your Scanfile.Bat
file along with your scanner then follow this simple rule. Change back to
the Node's directory at the end of the batch file. The following example
will help you to understand what I mean:
cd\wc30\wcwork\node%wcnodeid%
catscan %1
cd\wc30
{ some other utility autodesc, etc. }
cd\wc30\wcwork\node%wcnodeid%
If you are not running some other utility after your scanner then you
don't have to worry about changing back to the Node's directory.
┌──────────────┐
│ UPLOAD NOTES │
└──────────────┘
Through the use of PREHSCDN.EXE, a single selectable upload area is
supported, so the user may upload to an area of their choice that they
have access to normally. All uploads that occur during any one
session will go to the area that the user so chooses, they will only
be allowed to choose areas for which they have security for. This
means for each HSLINK session they can select the area they want to
upload too.
Save Upload's to Which Area ("?" for Choices) ?
[1] New Uploads [26] Sysop Only!
They will only be shown areas for which they have security for in WC!
* Wildcat in its wctext.dat tells the user to start the HsLink transfer
now! when download is selected. This occurs before the user is asked
by HsCats which file area to upload to. You can do what I did and use
your mkwctext and change the prompt # 542 to one that will not cause
a conflict, such as:
"HsLink & BiModem User's, StandBy to select an upload area! (CTRL-X) aborts!"
So there you have it in a nut shell. It is easy to setup and totally
worth the effort!!!! If you should have any questions please feel
free to call me and I will help you out. I can be reached at my BBS
from 8pm till 8:00am (East Coast Time), Which at present is the only
hours my bbs will be up and running. PLEASE do not call anytime other
than the hours specified until I get another phone line installed.
The BBS # is (717)-731-8299 (19,200 V42/Bis) Good Luck and thanks for
supporting HSCATS, HSLINK & WILDCAT!
Enjoy! 04/12/92
Dale Fedorchik
The Cat's Castle BBS
Warranty
This is product is provided "as is" without warranty of any kind. The
entire risk as to the results and performance of the program is
assumed by you. Futher more, I the author do not warrant, guarantee,
or make any representations regarding the use of, or the results of
the use of the program, and you rely on the program and results
solely at your own risk. I the author cannot accept responsibility
for system damage, loss of profit, or any other special, incidental,
or consequential damages resulting from the use or inability to use
this product.